v1.17.0 Release Notes

Zadig v1.17.0 was released on April 4, 2023.

# Feature List

Workflow Feature List

• Custom workflows add built-in output variables (service/code information/environment name, etc.)
• Custom workflows support personal favorites
• Custom workflows support general triggers
• Custom workflows support operation logs
• Custom workflow execution supports selecting all service components
• Custom workflows add pending approval status
• Workflows support parallel deployment of Helm services
• Workflow Git trigger Push events support automatic cancellation
• Workflow task timeout includes environment preparation stage
• Workflow builds support configuring code repositories to not display during execution
• Workflow task cache configuration is disabled by default
• Test tasks support file storage capability
• Security scanning supports configuring multiple repositories
• Dashboard adds workflow execution status

Workflow Experience Optimization

• Workflow deployment task status optimization with enhanced Pod event checking
• Workflow list page display efficiency optimization
• Workflow list page displays recent ten task information
• Workflow task list page supports stage information
• Workflow task detail page UI optimization
• Workflow configuration and execution error information optimization
• Workflow log /r line break display optimization
• Workflow task required content validation added
• Custom workflow approver count check optimization

Services and Environment

• Deprecated shared services
• Environment supports personal favorites
• Environment page service list scrolling interaction optimization
• Helm Chart project add service interaction optimization

Other Optimizations and Bug Fixes

• Project search supports Chinese
• Image registry integration adds address validation
• Permission configuration UI optimization
• Fixed custom workflow execution cross-project testing error issue
• Fixed Gerrit patch set events unable to trigger workflow issue
• Fixed missing PR information in notifications when workflow executes multiple PRs
• Fixed workflow not triggering properly when creating tags based on non-master branches
• Various experience and interaction optimizations

# Business Change Notice

The shared service functionality in K8s YAML scenarios has been deprecated in the new version. Service data will not be affected after upgrade. If you are using this feature, after upgrading, configure builds for the service in the referencing project. Build configuration can be found in: Build Configuration.

# Version Upgrade Process

# Database Backup

If already in production use, be sure to backup the database before upgrading

1. Database backup commands:

• Backup MongoDB data

mongodump -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE -o FILE_PATH

• Backup MySQL data

mysqldump -h <HOST> -P <PORT> -u root -p user > user.sql
mysqldump -h <HOST> -P <PORT> -u root -p dex > dex.sql

2. Database restore commands:

• Restore MongoDB data

mongorestore -h IP --port PORT -u USERNAME -p PASSWORD -d DATABASE --drop FILE_PATH

• Restore MySQL data

# Execute the following in MySQL:
mysql> drop database user;
mysql> create database user;
mysql> drop database dex;
mysql> create database dex;
# Execute the following data recovery operations from command line:
mysql -h <HOST> -P <PORT> -u root -p user < user.sql
mysql -h <HOST> -P <PORT> -u root -p dex < dex.sql

# Upgrade Operations

Please execute corresponding upgrade steps according to different installation methods.

# Installation Method: All in One Installation Mode or Installation on Existing Kubernetes

For both installation methods, use the script from Installation on Existing Kubernetes^New for upgrade.

# Installation Method: Helm Command Installation

For this installation method, execute the following steps to upgrade to v1.17.0:

1. Execute the following command to backup installation parameters and save as zadig.yaml file.

helm get values <Release Name> -n <Zadig Namespace>  > zadig.yaml

2. Execute upgrade command according to installation method.

• Domain method:

export NAMESPACE=<Zadig Installation NAMESPACE>

helm repo update
helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} --version=1.17.0

• IP + PORT method:

export NAMESPACE=<Zadig Installation NAMESPACE>
export PORT=<Any port between 30000-32767, different from initially used port>

helm repo update
helm upgrade -f zadig.yaml <release_name> koderover-chart/zadig --namespace ${NAMESPACE} \
    --set gloo.gatewayProxies.gatewayProxy.service.httpNodePort=${PORT} \
    --set gloo.gatewayProxies.gatewayProxy.service.type=NodePort --version=1.17.0